I would recommend not modifying the player.Scale but instead adding FpcRole::Scale

I concur, tbh I think we need something like Dictionaries to track player scales to re-create pre 14.1.1 behavior, but Bonjemus said he wanted a way to not have scale persist so we should just add an overload for that in the SetScale method, we could also add a GetScale(Player observer) method for devs to get a players scale / fake scale after setting it

I would recommend not modifying the player.Scale but instead adding FpcRole::Scale

That would be a breaking change, I don't get what you mean.

I concur, tbh I think we need something like Dictionaries to track player scales to re-create pre 14.1.1 behavior, but Bonjemus said he wanted a way to not have scale persist so we should just add an overload for that in the SetScale method, we could also add a GetScale(Player observer) method for devs to get a players scale / fake scale after setting it

As aforementioned, maintaining the scale after a role change is sloppy and will lead to a lot of confusion/errors.

I would recommend not modifying the player.Scale but instead adding FpcRole::Scale

That would be a breaking change, I don't get what you mean.

Brother this PR is already a breaking change, my suggestion might be "sloppy and will lead to a lot of confusion/errors" but at least it would lead to non-breaking behavior with more features

this update introduces a serious issue, where modifying Scale more than twice within a frame will cause the server to crash

Yes, this is NW issue, yes, this was already talked in the message (read please) m, yes, some code (like in custom role) has been adjusted to avoid crashes. NW said it will be fixed next update. READ.